You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Slack-specific types (rich-text, channels, usergroups) found in Schame.slack.types are not easily discoverable. This is partly caused by them being separated from primitives (string, boolean, etc.) found in Schema.types
Alternative solutions
Aliasing Schame.slack.types to Schema.types.slack could improve discoverability of Slack-specific types (rich-text, channels, usergroups). The goal would be to make Slack-specific types "sub-types" of the Schema.typesprimitives (string, boolean, etc.). This would make the developers autocomplete recommend Slack-specific types in Schema.types
Description of the problem being solved
Slack-specific types (rich-text, channels, usergroups) found in
Schame.slack.types
are not easily discoverable. This is partly caused by them being separated fromprimitives
(string, boolean, etc.) found inSchema.types
Alternative solutions
Aliasing
Schame.slack.types
toSchema.types.slack
could improve discoverability of Slack-specific types (rich-text, channels, usergroups). The goal would be to make Slack-specific types "sub-types" of theSchema.types
primitives
(string, boolean, etc.). This would make the developers autocomplete recommend Slack-specific types inSchema.types
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
The text was updated successfully, but these errors were encountered: