- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.2k
          Remove v10 legacy custom properties
          #8374
        
          New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    
                
     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
    
  
  
    
    v11 legacy custom properties
      …emove-v11-legacy-custom-properties
…emove-v11-legacy-custom-properties
              
                    lgriffee
  
              
              commented
              
                  
                    Mar 13, 2023 
                  
              
              
            
            
        
          
                ...m/content/tools/stylelint-polaris/rules/colors-declaration-property-value-disallowed-list.md
              
                Outdated
          
            Show resolved
            Hide resolved
        
      v11 legacy custom propertiesv10 legacy custom properties
      
  This was referenced Apr 19, 2023 
      
      
     Merged
  
      
        
      
      
  
    5 tasks
  
…emove-v11-legacy-custom-properties
              
                    alex-page
  
              
              approved these changes
              
                  
                    Apr 20, 2023 
                  
              
              
            
            
| ✅ Will wait on #9017 shipping so we can remove legacy motion tokens as well before shipping. | 
…emove-v11-legacy-custom-properties
| Going to wait on shipping this until we have  | 
Co-Authored-By: Aaron Casanova <32409546+aaronccasanova@users.noreply.github.com>
Co-Authored-By: Aaron Casanova <32409546+aaronccasanova@users.noreply.github.com>
Co-authored-by: Aaron Casanova <32409546+aaronccasanova@users.noreply.github.com>
Co-authored-by: Aaron Casanova <32409546+aaronccasanova@users.noreply.github.com>
              
                    aaronccasanova
  
              
              approved these changes
              
                  
                    Apr 24, 2023 
                  
              
              
            
            
  This was referenced Apr 25, 2023 
      
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      
  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.
  
    
  
    
WHY are these changes introduced?
Fixes #8405
Closes #4826
WHAT is this pull request doing?
Removes the legacy custom properties outlined in #8405 from v11.