Giter Club home page Giter Club logo

server-sass's People

Contributors

andyha avatar hggh avatar jakobvogel avatar mkeckmkeck avatar mulderbaba avatar sabieber avatar t0xa avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

server-sass's Issues

Missing support for relative scss file path resolution in the import part

It seems there is no support for relative scss file path resolution in the import part if the baseDir set.

For example:
File a/b/c.scss: @import '../../test/test';
File test/_test.scss: a {}

It couldn't find the file test/_test.scss, it will only look the file up in the directory baseDir/../../test, not baseDir/test. What's more, it couldn't deal with the underscore prefix for non-output scss file automatically, to my opinion. However, it seems easy to fix the bug. Working on it, hahaha

Incorrect nesting CSS rule exported

Source:
a
{
b
{
background-image: url('test.png');
#:hover
{
color: red;
}
}
}

Export:
a b
{
background-image: url('test.png');
}

a a b #:hover
{
color: red;
}

The second rule is incorrect

Non standard project directory structure?

Hi Andreas,

Is there a reason for non standard project directory structure?

  • pom.xml and build.xml are not in root directory
  • library artifacts in lib folder
  • src and test are separate folders

Do you prepare and upload releases to maven central manually?

Thanks,
Anton

Please document which features are present and/or missing from Sass

Hi there!

I'm one of the Sass developers and we love it when people love sass enough to build alternate implementations. However, we get a lot of support requests from people who think they are using a compliant version of Sass but aren't and it isn't until we've done a number of debugging back-and-forths that it comes out that they're actually using something that doesn't properly implement the language.

We have an effort to develop a standardized test suite for alternate implementations. Would you be willing to help us on that? The goal will be to test for compliance as well as document in a user-friendly fashion the differences so that users can make an informed decision about whether they should use your project.

More information:
sass/libsass#282
https://github.com/hcatlin/sass-spec

This will help us keep the Sass community strong and vibrant. Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.