Added Facebook sample connector #7
Merged
Conversation
This file contains hidden or 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
|
Please remove the settings.json. Is the icon the default icon? Otherwise, please remove the icon or replace with default one. |
Removed settings file, yes the checked in icon is the default custom connector icon |
| @@ -0,0 +1,435 @@ | |||
| { | |||
There was a problem hiding this comment.
Couple of generic comments... Lets change the sample name form FacebookConnector to just Facebook
Dont include the generic icon file
| "oAuthSettings": { | ||
| "clientId": "{facebook_app_client_id}", | ||
| "customParameters": {}, | ||
| "identityProvider": "facebook", |
There was a problem hiding this comment.
Dont we need clientSecret?
There was a problem hiding this comment.
No, client secrets need to be provided as command line parameter
There was a problem hiding this comment.
Yes. The CLI will ask for it when not provided. This is to avoid inadvertent saving of secret in api prop file.
| "authorizationUrl": "https://graph.facebook.com/oauth/authorize", | ||
| "flow": "accessCode", | ||
| "scopes": { | ||
| "user_posts publish_pages publish_to_groups": "user_posts publish_pages publish_to_groups" |
There was a problem hiding this comment.
Interesting... do we need Security definition in swagger?
There was a problem hiding this comment.
I have added the files as they were downloaded via CLI tool.
There was a problem hiding this comment.
This is the original swagger, without any modification. Do you think it is not expected?
dmkuby
reviewed
Mar 29, 2019
sriharip-docusign
referenced
this pull request
in release-docusign/PowerPlatformConnectors
Apr 18, 2023
Merge SMS related code changes from Angel + Custom field bug fixes
harshitav-docusign
referenced
this pull request
in release-docusign/PowerPlatformConnectors
Apr 21, 2023
Flow-366: c2 : list envelope documents
vmanoharas
pushed a commit
that referenced
this pull request
Oct 3, 2024
* - First pass at getting all partitions. Still needs a few parameters setup so the code is currently broken. WIP. * Update script.csx Convert all partitions, not just the first one. * Update script.csx Fix placeholders of querystring params that need gotten/set for fetching subsequent partitions. * Update script.csx Fix syntax errors to ensure that isn't why connector upload is failing. * Update script.csx Fix more compilation errors. * Update script.csx Wanted a record of the fact that these changes are still returning subsequent partitions in array format, despite literally every response being converted. Is there maybe some sort of caching of the connector behavior, because it seems like I can't ever get the behavior of my data flow to change at all... * Update script.csx This version of the connector is the most complete example that can successfully be uploaded as a custom connector. Yet I still can't get the behavior to change no matter what code changes I make. * Issue #5 - Null detection and Type Conversion Error (#1) * Update script.csx - Fix null detection. * Fix issue with null handling in Snowflake connector --------- Co-authored-by: jbrinkman <github@brinkman.me> * Update apiDefinition.swagger.json - This version of the swaggerjson SHOULD be working, but we are seeing the DataSchema object being flattened out once uploaded to customer connector. * array data for DataSchema Got the swagger right (was really the code was had checked in before with just a little cleanup. The custom connector is now failing due to internal server error so we need to find a way to use the test page in powerapps online, despite the fact that it doesn't really handle array data very well. Possibly specifying the raw body data might be a workaround. * Update script.csx - Last few tweaks to get the customer connector to return subsequent partitions in pre-converted format. * Add version information into readme documentation * cleanup endpoints - extra body element is required. Caused a whole mess of issues. - change DataSchema to required and deprecate or delete unused endpoints as needed. - Remove fetchAllPages feature and separate into its own branch. * Code cleanup. - Make log messages more accurate. - Remove last remnant of fetchAllPartitions. * code cleanup * more minor code cleanup * intermediate check in - The code is acting absolutely insane and returning GetResults method as just a single property "Data" formatted as array. Since this is the 0 partition it should include metadata. - The interface is also not showing the partition parameter for the execsql method, so something is borked. * GetResults partition zero fixed - This was a very subtle issue related to the fact that when you call GetResults operation for partition zero you have no request body, so it cannot be parsed as json. - Change the response of execstmt async to match the schema of the sync version b/c the powerapps ui does not seem to be able to deal with the fact that async/sync have different response formats respectively. * SPC-36: Handle unexpected async responses better (#5) * Update script.csx - Fix async detection based on response code instead of request params, b/c apparently snowflake API can decide to return an async response if a synchronous response takes too long to return. * Fix typo in script.csx "BeginFetch" misspelled --------- Co-authored-by: Joseph Brinkman <github@brinkman.me> * SPC-39: MULTI_STATEMENT_COUNT parameter was being ignored (#6) * Update apiDefinition.swagger.json - change parameter name case to match snowflake docs exactly * add StatementHandles Map new response property for multi-statement handling. * Apply mappings to GetResults Same statementHandles mapping that was previously added to ExecSql was applied to GetResults to support Async * Remove async fixes These changes are already in dev branch, it was just a temporary change for debugging. * GetResults schema (#7) Innacurate schema was causing compilation issues in the power apps. Better to leave it as a untyped object since the schema is dynamic. * - Parse Object/Array types (#8) They were represented as a string before. * Document limitations per my experience. (#9) * Document limitations per my experience. * - Tweak readme * Update language limitations in the Readme documentation. --------- Co-authored-by: jbrinkman <github@brinkman.me> * openapi spec validation errors (#10) I was able to type the untyped objects, but a lot of those openapi spec validation errors are inherent to the fact that the snowflake api routes are technically all partial matches for eachother since the exec stmt path is "/" * Updated version history * Fix typo --------- Co-authored-by: TobinWritesCode <tobin.chee@improving.com>
vmanoharas
pushed a commit
that referenced
this pull request
Jul 25, 2025
…imary Key, fix datasets metadata (#3940) * FLOW-4100 Improve detecting of table primary key (#4) * FLOW-4393 Provide versioning and version identification for Power Apps Connector (#6) * Add Versioning * fix build * FLOW-4102 Fix datasets metadata endpoint to return correct values (#7) * Bump Snowflake Connector version 2.2.0 (#8) * Snowflake V2 Add apidefinition contact and categories --------- Co-authored-by: Piotr Zalas <127133187+sfc-gh-pzalas@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.