Add Argument for Filtering Token Types

[apackin]

Addresses #32

Pull Request: Add Argument for Filtering Token Types

Overview

This pull request introduces a new argument, filteredTokenTypes, to exclude specified token types from parsed results:

• New Argument: filteredTokenTypes
• Functionality: Omits specified token types from processing
• Usage: --filtered-token-types=core,source

Files Modified

1. bin/figma2flutter.dart

   • Main Function:
     • Added filteredTokenTypes option
     • Parsed argument into a list of token types
     • Passed filteredTypes to _processTokens
   • Token Processing:
     • Implemented filtering logic in _processTokens

2. lib/config/options.dart

   • Option Definitions:
     • Added filteredTokenTypes constants and option for configuration

3. lib/processor.dart

   • Processor Class:
     • Updated process method to accept filteredTypes
     • Added logic to remove tokens based on filteredTypes list

Example Usage

To run the tool and exclude tokens of types core and source:

dart bin/figma2flutter.dart --filtered-token-types=core,source

This will filter out tokens with paths starting with core or source.

Conclusion

These updates provide more control over the token processing, enabling users to fine-tune their output. Please review the changes and provide your feedback.

Notes:

I tried skipping reading the "Core" tokens altogether, but other tokens rely on their processing to assign the correct values.

[frederikstonge]

It's a bit too specific imo. Adding a filter options to filter an array of token types would be a better solution.

You have removed a lot of comments, I don't think it was necessary.

Please add unit tests.

Please update documentation.

[apackin]

Thank you for the quick comments. I made the recommended code changes. Let me know if that looks good and I'll update with tests and docs later

[frederikstonge]

Thank you for the quick comments. I made the recommended code changes. Let me know if that looks good and I'll update with tests and docs later

Looks good to me :)

[freemansoft]

Should this be filteredTokenPaths or filteredTokenSets in place of filteredTokenTypes?

This filtering does what? It filters out all the tokens that were part of a token set while letting them be used as a base value for tokens that are retained?

[apackin]

It filters out all the tokens that were part of a token set

Yes, that is the intended usage. Technically there isn't enforcement regarding whether the filtered out items were used as a base value for other tokens, so it could be used to omit sets for other reasons if those exist. Happy to rename to filteredTokenSets

[apackin]

I renamed the argument and added tests

[freemansoft]

Somehow this got dropped. Was just looking at this...

Is this filteredTokenSets or filteredTokenPaths? At a quick look this remotes tokens that start with a certain path/prefix. The naming implies that it is by type like "Color" or "Text" but it is the path instead, yes?