-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
0572b16
commit d714cf5
Showing
4 changed files
with
70 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
const groupBy = function (operation, meta) { | ||
let path = ""; | ||
operation.tags.forEach((t, i) => { | ||
// build path | ||
path += t + "/"; | ||
}); | ||
path = path.replace(/\/$/, ""); | ||
return path; | ||
}; | ||
|
||
module.exports = groupBy; | ||
|
||
// ******************** | ||
// testing | ||
// ******************** | ||
|
||
|
||
const testData = { | ||
"tags": ["Posture Profile", "Browser"] | ||
} | ||
console.log(groupBy(testData)) | ||
// Posture Profile/Browser |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Overview | ||
|
||
In our pursuit to offer a seamless digital experience, we have introduced a new concept of **Integrated APIs** within the `api.meraki.com` namespace. | ||
|
||
These APIs are distinctive as they serve as seamless connectors to various systems, effectively bridging the gap between the multitude of software solutions we encounter. | ||
|
||
## Features and Considerations | ||
|
||
1. **Passthrough Nature:** Integrated APIs are primarily designed to be passthrough conduits to other systems within the api.meraki.com namespace. | ||
|
||
2. **Early Access Gated:** Due to the nature of the Integrated API endpoints, they don't fully comply with the Meraki API standards and serve as "Early Access" endpoints. | ||
|
||
3. **Fluidity in Design:** Given their early access phase, users should be aware that the Integrated APIs are fluid and subject to changes at any moment. This inherent nature allows us to adapt and innovate faster. | ||
|
||
4. **Transitioning Over Time:** We aim to improve and evolve continually. As such, over time, Integrated APIs will either be phased out or replaced by APIs that fully align with the Meraki API standards. | ||
|
||
5. **Documentation Process:** Our commitment is to provide a clear understanding of the Integrated API endpoint functionality. | ||
|
||
6. **Response Data Inclusion:** The response payload from the Integrated API may consist of data sourced from the various systems it interfaces with. | ||
|
||
Integrated APIs, while transitional, play a pivotal role in our current digital ecosystem. They act as the intermediary bridge, ensuring systems communicate effectively. As we progress, we invite our users to explore, utilize, and provide feedback, aiding in the evolution of Meraki's digital solutions. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters